added dotkernel.com packages - #10

@kakapiciu please check this and if is ok, approve and merge

@arhimede
everything in this repo up until now is design to help development on these dotkernel`s tools:

• Dotkernel API
• Dotkernel Admin
• Dotkernel Queue
• Dotkernel Light
  from previous meetings i understood that we can avoid Dotkernel Frontend ( correct me if i`m wrong )

dotkernel-packages skill it's useful solely inside dotkernel/dotkernel.com -> which seems to be build on Dotkernel frontend

dotkernel-package-status could be usefull BUT there are 4 conflicts with dependency-policy:

1. working with the same filename dependency-policy/references/dotkernel-packages.json vs dotkernel.com/dotkernel-packages.json both containing .packages[] array so it wont throw an error right away but start processing
2. they disagree on "safe to use" => dependency-policy judges by abandoned + release recency + PHP constraint...package-status judges by declared lifecycle and GitHub archived
3. direct contradiction on successors:
   dotkernel-package-status says "- For "what should I use instead?", the listing gives no successor field.
   Say the package is archived or security-only and point at the GitHub url and the lifecycle page rather than inventing a replacement."
   dependency-policy say "3. Check abandoned / replacement before proposing anything."
4. "not listed" means something different in each => packagist covers published packages including ones with no OSSMETADATA...the site covers only OSSMETADATA repos minus ignoreRepos.

ok, then

1. work with @bidi47 to fix the dotkernel-package-status issue
2. indeed frontend is not inportant
3. everything need to be installable and usable by someone not familliar with Dotkernel nor Claude

@arhimede , we discussed a solution. please confirm it sound ok

• link dependency-policy skill with dotkernel-package-status
• keep dotkernel-packages only in dotkernel.com repo